You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
open self-destruct-instance.example in web browser and see that it displays the message "This server is closing down" etc.
curl -vvv 'https://self-destruct-instance.example/users/someone' shows that the page returns status 410
curl -H 'accept: application/activity+json' -vvv 'https://self-destruct-instance.example/users/someone' shows that the page returns status 500
NB: The actual request for step 3 was slightly different, e.g. it additionally had a HTTP signature. This does not seem to change the outcome, so I take this as a minimum (non)working example.
Expected behaviour
returns status 410 to indicate that the user and instance are gone
Actual behaviour
returns status 500, indistinguishable from a temporarily malfunctioning server
Detailed description
No response
Mastodon instance
social.dev-wiki.de
Mastodon version
not able to determine
Technical details
The returned status 500 leads to my Activitypub implementation re-trying to process the activity several times. If a client error status code (4XX) was returned, processing the activity could correctly be scrapped immediately.
The error occurs on a Delete activity of an actor that my instance already deleted or otherwise didn't know and was thus first trying to fetch the keys to verify the signature. In trying to fetch the key, the request from the steps for reproducing was made.
The text was updated successfully, but these errors were encountered:
Steps to reproduce the problem
curl -vvv 'https://self-destruct-instance.example/users/someone'
shows that the page returns status 410curl -H 'accept: application/activity+json' -vvv 'https://self-destruct-instance.example/users/someone'
shows that the page returns status 500NB: The actual request for step 3 was slightly different, e.g. it additionally had a HTTP signature. This does not seem to change the outcome, so I take this as a minimum (non)working example.
Expected behaviour
returns status 410 to indicate that the user and instance are gone
Actual behaviour
returns status 500, indistinguishable from a temporarily malfunctioning server
Detailed description
No response
Mastodon instance
social.dev-wiki.de
Mastodon version
not able to determine
Technical details
The returned status 500 leads to my Activitypub implementation re-trying to process the activity several times. If a client error status code (4XX) was returned, processing the activity could correctly be scrapped immediately.
The error occurs on a
Delete
activity of an actor that my instance already deleted or otherwise didn't know and was thus first trying to fetch the keys to verify the signature. In trying to fetch the key, the request from the steps for reproducing was made.The text was updated successfully, but these errors were encountered: